DEVELOPER TOOLBOX, VERSION 6.1, SEPTEMBER, 1996

Table Of Contents 







How to Get Started




To use these CDs to their fullest, you need to run IRIX 6.2(TM)



Remember the living MASTER
WEB HOUSE exists at 
https://www.sgi.com/toolbox/








NOTE:  Please be aware there are three versions of this 
file.  The printed liner notes are cast in concrete first, then the CD version,
<CDROM>/toolbox/linerNotes.html, gets snapped.  The web house 
version, https://www.sgi.com/toolbox/linerNotes.html,
is never frozen, and is always the definitive source for these notes.  It
is a virtual certainty that these hardcopy notes will not contain ALL
the information and details that will exist in both of the other two sources
listed above.  Please refer to them where and when possible.





 -- For People With Less Than 3 CDROM Drives --


Please read about invoking viewDT, 
and understand how to ensure


correct content downloading from the 
DT v6.1 CD Pitfalls explantion.







Step 0 - Select a CD





Step 1 - Run the CD
























welcome to the 
 
version 6.1


September, 1996




On-line version of v6.1 CD Set Liner Notes






THE TOOLBOX JANITOR extends sincerest greetings to all, and
hopes the organization and presentation of information herein
provides an essential and ever-increasingly effective resource.






   The Developer Toolbox is a publication 
 produced for all registered Silicon Graphics® software and 
 hardware developers by the Silicon Graphics
 Developer Program. The 
 raison d'être of the Toolbox is to serve as an information resource, 
 providing an ever-expanding library of learn-by-example materials, as well as
 a wide range of technical information, for people endeavoring to create
 applications to operate on Silicon Graphics systems.  The formal
 mission statement of the Toolbox is

 

 
 To provide members of the developer program with detailed technical 
 information on a timely basis.  The toolbox includes proprietary, 
 unpublished, and published materials from a wide variety of SGI 
 sources presented in a one-stop-shop framework.  This information 
 fundamentally includes learn-by-example and actual application 
 source code, as well as proprietary and published documentation, 
 software in inst image format, and useful utilities.
 
 





   The Toolbox contains Silicon Graphics source code (plus compiled 
 executables), technical documentation (unreleased as well as released), 
 public domain source code (ported to the IRIS®), data file sets (audio, 
 inventor, image, geometry), web-related information (HTML, http, cgi-scripts), 
 and utilities (where source isn't available) plus inst software, for the 
 purpose of helping developers learn about, and implement code for, IRIS 
 workstations.  This software and information is intended for use by both 
 beginning and advanced IRIS programmers.  The philosophy driving the ongoing 
 creation and production of the Toolbox is to provide our developer community 
 with as much leading/bleeding edge software, hardware information, 
 documentation, FAQ lists, binary tools and utilities not available to the 
 general Silicon Graphics customer base so they are as "up-to-the-minute" as 
 possible in understanding where Silicon Graphics is going.  








                           DT v6.1 ==> IRIX 6.2









   Except for the binaries in each CD's /CDROM/bin directory -- which provide
 the "web-accessibility" to the DT via the viewDT script and the Netscape Navigator Client, 2.02S software (which 
 is IRIX 5.3-based) -- v6.1 of the Developer Toolbox is entirely built upon 
 IRIX 6.2.  These binaries -- the compiled programs in the bin/, documents/video/lurker/ij/, hardware/{dat.kernel/, 
 mount_media/{cdmount/, 
 mountMO/}, parallel_port/, summa/test/}, public/TIFF/tools/, src/, and 
 utilities/CDmastering/ 
 sub-trees/directories -- will not run correctly on prior versions of 
 IRIX.  For those of you still on IRIX 5.3, most of the program's source code 
 has not changed (see /toolbox/DTinfo/DT6.2port.html#CHNGED 
 for a list of what source code/Makefiles did change) so you can copy same 
 onto to your local disk in order to re-compile an IRIX 5.3 
 version.  Further, the 6.0 DT Web-on-CD has a complete 5.3 version of all 
 this source aside from any added new stuff.




   v6.1's biggest claim to fame is that it is the first toolbox to move up to
 the world of IRIX 6.2.  The toolbox source, build, test and 
 SGI-internal-website
 machine, named dtdustbin and aliased as "swank", is an IP19 6-processor 
 Challenge-L system.  In May, we upgraded swank to IRIX 6.2, changing the 2GB 
 system disk to be an xfs filesystem in the process.  After the Developer 
 Forum we began the process of re-compiling all source code on the DT with the 
 "bare-bones", "just compile-and-run on a 64-bit system without reaping 
 any of its new benefits" O32 (-mips2 -o32) default IRIX 
 6.2 compiler settings defined in /usr/include/make/releasedefs.  In 
 qualifying what we mean here by the slippery-to-some-people "64-bit system" 
 term, it is useful to quote from that grand-vizier-at-large Dave "Guru and busybody at 
 large" Olson, when he
 clarified this point in the sgi.engr.devp internal newsgroup,

 

 
   The problem is how you define 64 bit.  Some people still want to
   assume that 64 bit means 64 bit addressing.  64 bit can also be
   interpreted to mean 64 bit busses or i/o paths, and we've had that
   on all of our r4k and later systems.  It can also be interpreted to
   mean 64 bit integer operations, loads, stores, etc., and we have that
   on all systems in 6.2 with N32.  It can also be interpreted to be large
   files and filesystems, and we have that (although not quite as large
   on the 32 bit OS desktop machines;  they are large enough.)

   

   
   The only thing that is not 64 bit about the desktop r4k systems in 6.2
   is the address space.  I'm not saying that this is unimportant, but it
   IS only one portion/definition of being 64 bit, and it's important
   that everybody understand the distinction, particularly if you are
   working with developers.  It's also important that you understand how
   and why we are positioning 6.2 as 64 bit on all platforms.  And no,
   I'm not a pod.  I believe you can be 64 bit, without having 64 bit
   addressing, for the vast majority of apps.
 
 


See What We Did to Port the 
Developer Toolbox to IRIX 6.2 for all the details about what 
we did and learned about in order to recompile the DT src on
IRIX 6.2.




In re-compiling the DT binaries on IRIX 6.2, we are increasing 
our emphasis to you, our developers, of the importance of porting
your applications and environments to an IRIX 6.2, all R4000 and
higher platforms' universe, since this will be the native Operating 
System for all upcoming Silicon Graphics products.  Such systems 
won't know a thing about the "IRIX 5 dimension".  Hence, the 
sooner your programs can compile on IRIX 6.2 -- even with just 
the "bare-bones" O32 option -- the sooner you'll be able to take 
advantage of the "next generation" of SGI machines debuting later 
this year.  The other central fact about this situation is that
ELF binaries compiled on 
IRIX 5.3 will run correctly on IRIX 6.2.  But the best 
strategy is to qualify existing 5.3 based binaries on 6.2 to 
support existing platforms and begin the effort to move 
forward with SGI in the near-term future.




In all our efforts to complete a sufficient "baseline" to ship in 
v6.1, we were unsuccessful in re-compiling anything as N32 -- we
did do an entire pass of the tree using make -i, 
but a significant number of "Warning" messages using O32 turned into 
"Fatal Error" messages with N32.  This is the work before 
ALL of us.  For our part, this fall we will create an 
"N32 Progress" page in which we include links to those programs
which are "N32-compliant" as we are able to clean up
current DT source, as well as add in new N32-created 
programs.  Another component of this "N32 transition puzzle" that
will help all of us is the mongoose MIPS PRO 7.0 compiler, 
since it compiles faster, and in less memory, than the ragnarok 
compilers that shipped with IRIX 6.0.1-6.2.








                            site licensing








Many of you would like to be able to serve the contents of the Developer
Toolbox from your local website.  Here is what is required.

    
       
  1. Security and Your Liability

    
           The information contained in the Developer Toolbox can only be 
	   used by current members of the Developer Program. This means it
           can only be made available to employees of your company.
           For instance, it is a violation to place the contents of the
           Developer Toolbox on your local web connected to the Internet,
           without an appropriate firewall or a secure server.  Be sure you are 
	   well-versed on the Developer Toolbox Terms
	   and Conditions of Use and Disclaimer, i.e. failure to adhere
	   to these Terms and Conditions could result in financial liability
	   for you and/or your company.

    
       
  2. The Absolutely Easiest Way to "Pseudo-Serve" the DT

    
           Suppose you have 3 CDROM drives available on one or more
	   systems on your local area network.  And further, suppose
	   these 3 CDROM are dedicated to serving the Developer Toolbox
	   CDs.  Then, all you have to do is place one CD in each CDROM
	   drive and make sure they are exported (so they can be seen
	   by any other system).  From any machine with automount running 
	   you could run:  /hosts/sgi_dt/CDROM/bin/viewDT to 
	   start viewing the Toolbox where 
	   one of its CDs is loaded on the CDROM drive
	   connected to the machine named "sgi_dt".  You supply the paths 
	   to other CDs when dtCDmgr asks for them.  As long as the CDs
	   stay put in their respective CDROM drives, you would only need 
	   to do this once as dtCDmgr remembers where to look for the CDs
	   that have already been specified in a previous session.

    
       
  3. An Easy Way to "Pseudo-Serve" the DT

    
           Just copy each CD to a separate directory on disk. 
	   
    
	   For example, let's suppose you are using the sgi_dt machine as the 
	   server, that it has automount running, and that you have copied 
	   the CDs to sgi_dt:/dt_6.1/cd0, sgi_dt:/dt_6.1/cd1 and 
	   sgi_dt:/dt_6.1/cd2.  From any machine with automount running you 
	   could run:  /hosts/sgi_dt/dt_6.1/cd0/bin/viewDT to 
	   start viewing the Toolbox.  You supply the paths to other CDs 
	   when dtCDmgr asks for them.  As long as the CDs stay put in their 
	   respective CDROM drives, you would only need to do this once as 
	   dtCDmgr remembers where to look for the CDs that have already 
	   been specified in a previous session.

    
       
  4. Serving the DT on your web

    
           This is a more complicated process involving the running
           of the oksvr server search engine along with necessary cgi-bin
           scripts from /toolbox/www/cgi-bin.  To do this 
	   correctly will require work on both your and our part since 
	   each website will have unique site-specific details to 
	   decide upon and configure.  We have opted not to tackle this 
	   route in the v6.1 release.  The possibility exists that we will
	   succeed in creating the "how to" process write-up to document 
	   implementing this before the v6.2 DT Web-on-CD release at 
	   year's end.  Stay tuned to the Toolbox web site's NEW page for updates regarding 
	   this.
	   
    
	   The possible downside of the previous two methods is that 
	   separate HTTPD and oksvr servers are created with each viewing 
	   of the toolbox.  It would be cleaner to just have a single 
	   version of each server (as we do with our main website, https://www.sgi.com/toolbox/).










                              multiple CDs








   The /CDROM/bin/viewDT DT-viewing mechanism, along with its cohort the
 dtCDmgr program, have both experienced a great deal of "maturing" since 
 v6.0 to provide a more seamless access mechanism for sifting the contents 
 of the DT.  We greatly appreciate the support of those developers who
 helped us nail down the problems some of you experienced with the vagaries
 of v6.0's viewDT script. 




 If you have 
 more than one CDROM drive accessible by your machine on your Local Area 
 Network, you can put these CDs into the available drives, and inform 
 viewDt, specifically dtCDmgr, of all of their locations when it prompts 
 you for a particular needed CD.
 You will then be able to explore all the contents as if you had this 
 DT nfs-mounted on disks from other machines.  If you only have one CDROM 
 drive, the dtCDmgr will prompt you to switch CDs whenever you access a link 
 pointing to a file on a CD other than the one currently loaded.  (See
 the v6.1 contents of the /CDROM/bin/helpfile file included in 
 the back of these liner notes for details 
 about the operation of all this.)




   For those of you who have already received v6.0 and it's binder, we've
 designed v6.1 to be inserted into it following the v6.0 release.  For the
 artwork and production of v6.1 we are deeply grateful to artist Tim Racer
 (our on-going "hired gun" visual wizard who painted the binder's cover as
 well as the v6.0 divider) and the steadfast help, creativity, and 
 resourcefulness of Sophie Lonsky, Amy Gregg, and Jenifer Bailey.
 embarkation of ratmandu and whitewolf 









HUB |
Pheedbak |
Tree |
Topic |
A-Z |
Search |
Hot |
New |
FAQs |
Jumpdoors























VERSION 6.1 NEW ADDITIONS:












DOCUMENTATION:




SRC:





BINARIES:





INST IMAGES:





























                 also included (pre-version 6.1 vintage):































  • 64 Bit:




    


  • IRIX 6.2 documents:




    


  • IRIX 6.2-based software:




    


  • Silicon Graphics Pipeline Articles:




    


  • MIPS ABI documentation + patches subtree



    


  • educational/tutorials software:




    


  • texture mapping / 
volume rendering:




    


  • R10000 Microprocessor Documentation:




    


  • Hi End Graphics Systems doc:




    


  • Optimization / Performance Tuning:




    


  • utilities[+src]:




    


  • Viewkit:




    


  • public:




    


  • image data:




    


  • OpenGL documents:




    


  • OpenGL src:




    


  • paul haeberli's universe/image 
stuff:




    


  • video:




    


  • audio:




    


  • X:




    


  • hardware:




    


  • network:




    


  • WWW:




    


  • Performer:




    


  • PERL:




    


  • MAC:




    


  • General IRIX/C/CC:




    


  • IRIX 5.3:




    


  • Open Inventor:




    


  • speech recognition:




    


  • software tools:




    


  • Silicon Studio(TM):



  • printers:




    


  • FAQs:




    


  • games:




    


  • exampleCode:




    


  • demos:




    


  • binaries:




    


  • Multi Processor 
implementations:




    

AND, other TOP-OF-TREE ASCII text information files besides this one:

    

    
ALL DTa-z* files have a .html form superior to the following;  

    
the .txt format is included for access-versatility.

    

    DTa-zAudio.txt:    DT sound files listed by directory
DTa-zDocs.txt:     documents listed by title 
DTa-zIV.txt:       Inventor .iv data files listed by directory
DTa-zImgsGIF.txt:  gif images (so many, so listed separately)
DTa-zImgsJPG.txt:  jpg images (so many, so listed separately)
DTa-zImgsRGB.txt:  rgb images (so many, so listed separately)
DTa-zImgsTIF.txt:  tif images (so many, so listed separately)
DTa-zImgHaeb.txt:  images in src/haeberli listing (info "richer")
DTa-zInst.txt:     inst images listed by directory
DTa-zLibs.txt:     library archives and DSOs listed alphabetically
DTa-zSrc.txt:      DT binaries listed alfabetically w/path-location

DThelp.txt:        Help topics relevant to the operation of the v6.1 CD
README:            this file in boring ascii text form
  
Makefile.README:   IRIX 5 gotcha's as far as MAKE(1) is concerned
README.Inventor:   how to compile with Open Inventor 2.0 and 
                     Inventor 1.1.2 libs + hdrs on the same machine
sifttree.README:   how to do multiple keyword/filename searches


    

    

    

    
   After sampling the software, you may want to copy some or all of the code
   from the CDROM to your workstation.  Although you may copy the software to
   any disk with enough space, it is intended to be copied into the
   "/usr/people/4Dgifts/toolbox" directory.  Local Makefiles are provided for
   all source code.

    

    

    
   Total size of the v6.1 DT is approximately 614+ megabytes on CD 0, 
   
    
   596+ megabytes on the CD 1, and 594+ megabytes on CD 2.

    


    


    

    

    

    

   Please find below the contents of the viewDT helpfile
   (/CDROM/bin/helpfile) and the dtCDmgr internal 
   helpfile as of September 25, 1996.  The helpfile available via the 
   "Help" button in the viewDT window will be more current than this version.  


    


    
    

    

    

    

start of viewDT helpfile (/CDROM/bin/helpfile)


    

    

    
The purpose of this "help" file is to provide information about
initiating viewing of the v6.1 CD form of the Developer Toolbox.
Areas discussed are:

    

    


    

    
    
0) if your CDROM drive is not mounted as /CDROM

    

    

    

    /dev/dsk/dks0d4s7 /CDROM efs ro,sock=/tmp/.mediadXXXXXX 0 0
/dev/rmt/tps0d5nr /tape archive opts=NA,sock=/tmp/.mediadXXXXXX 0 0

    



    

    
    
1) location of Developer Toolbox "help" documentation

    

    

     


    
    

    
2) prerequisites to satisfy before starting any viewing

    

      

      
   There are some prequisites you will want to ensure are satisfied 
   before you attempt to view anything on the Developer Toolbox.  There
   are two versions of the following information:  one for people 
   on a system running IRIX 6.2, and the other for people 
   running IRIX 5.3 (or anything else prior to IRIX 6.2).


      
      

      

      

    1. For people running viewDT on an IRIX 6.2 system:


      

      
      

        
     
      1. Make sure you have all the Netscape
	  helper programs installed.
	  
        
     
	You can verify you have IRIX 6.2-released versions of the 
	following subsystems containing the necessary netscape helper 
	apps by running the versions command and comparing the 
	described version numbers to the following:
	
        
	
          
	
        • showcase -- IRIS Showcase 3.4
	
            
	showcase.sw.showcase
	
          
	
        • inventor_eoe -- Inventor Execution Only Environment, 2.1.2
	
            
	inventor_eoe.sw.2_0
	
          
	
        • imgtools -- ImageVision Tools, 3.0
	
            
	imgtools.sw.tools
	
          
	
        • il_eoe -- ImageVision Library Execution Only Environment, 2.5.1
	
            
	il_eoe.sw.c++
	
            
	il_eoe.sw.tiff
	
            
	il_eoe.sw.sgi
	
            
	il_eoe.sw.jfif
	
            
	il_eoe.sw.gif
	
          
	
        • dmedia_eoe -- IRIS Digital Media Execution Environment, 6.2
	
            
	dmedia_eoe.sw.audio
	
            
	dmedia_eoe.sw.common
	
            
	dmedia_eoe.sw.lib
	
            
	dmedia_eoe.sw.soundscheme
	
            
	dmedia_eoe.sw.midi
	
            
	dmedia_eoe.sw.tools
	
            
	dmedia_eoe.sw.video
	
          
        
        • dps_eoe -- Display PostScript/X, 2.0.5 based on PostScript Level 2
	
            
	dps_eoe.sw.dps
	
          
	This subsystem is not needed for people who use something 
	other than xpsview(1) to view PostScript files on their 
	system.  You can arrange to use a different PostScript
	viewer via your personal $HOME/.mailcap file 
	and an appropriate substitute helper program (e.g. ghostview).
     
          
        It is worth mentioning that if you do not have your own
        $HOME/.mailcap and/or $HOME/.mime.types files,
        versions of these will be created for you.  $HOME/.mime.types
        is used to augment the global default definitions
        (/usr/local/lib/netscape/mime.types) of the file extensions 
	which correspond to a particular mime type.  $HOME/.mailcap
	is used to augment the global default definitions
        (/usr/local/lib/netscape/mailcap) of the mime types
        which correspond to a particular helper application.  There will be 
	some Toolbox-specific definitions added to both of these files to 
	help support the viewing of Developer Toolbox content.
	
        
     
     
      


      
      

      

      

    2. For people running viewDT on an IRIX 5.3 
   (i.e. a non IRIX 6.2) system.


      
      

      

      

        
     
      1. Make sure you have all the Netscape
	 helper programs installed.  

        
         (Available on the Descktop Special Edition (DSE) 1.1 CD)
     
        
     
 	You can verify you have sufficiently current versions of the 
	following subsystems containing the necessary netscape helper apps 
	by running the versions command and comparing 
	the described version numbers to the following:
	
        
	
          
	
        • showcase -- IRIS Showcase 3.3.3
        
            
	showcase.sw.showcase
	
          
	
        • inventor_eoe -- Inventor Execution Only Environment, 2.1.1
        
            
	inventor_eoe.sw.inventor
	
          
	
        • imgtools -- ImageVision Tools, 2.3
        
            
	imgtools.sw.tools
	
          
	
        • il_eoe -- ImageVision Library Execution Only Environment, 2.5
        
            
	il_eoe.sw.c++
	
          
	
        • dmedia_tools -- IRIS Digital Media Tools, 5.5
        
            
        dmedia_tools.sw.movietools
	
            
        dmedia_tools.sw.soundtools
	
          
	
        • dmedia_eoe -- IRIS Digital Media Execution Environment, 5.5
        
            
	dmedia_eoe.sw.audio
	
          
	
        
        
        
	If you do not have the above subsystems loaded, you can find them
	on the DSE 1.1 CD, the second CD included in the v5.1 DT.  It 
	contains all the inst images needed to satisfy the above 
	prerequisites.  
        
        
        If you do not have the v5.1 DT, look for a copy of the DSE 1.1 CD 
	with your collection of IRIX 5.3 CDs.  If it is not there, you can
	also access the DSE 1.1 contents at https://www.sgi.com/toolbox/DSE1.1/.  If you are unable to do this,  contact the Developer Program
	at devprogram@sgi.com, or
	on the phone either via 1-800/770-3033, or 415/933-3033, or by 
	fax via 415/969-6327, and tell them you need a copy of the DSE 1.1
	CD sent to you through the post. 
     
     
     
        
             
     
        
     
        

     
      2. Make sure you have all the appropriate patches installed.
     
        
     
         Not all subsystems in these patches will install -- you will 
	 only be allowed to install subsystems corresponding to base 
	 software already installed.  In other words, always attempt 
	 to install the entire patch and don't be alarmed about the 
	 parts which do not install.
     
        
         Some of the patch locations mentioned below also contain a 
	 recommended patch list.  It is helpful to know your hardware 
	 and O.S. level in order to install the recommended patches.  We 
	 are working to have this information included in the toolbox.  We 
	 do have an abbreviated list below of seven key patches for IRIX 5.3, 
	 current as of August 14, 1996.  All of them are replacements of 
	 similar IRIX 5.3 patches recommended in the v5.1 DT.  These patches 
	 are also available on the toolbox in /toolbox/dist/5.3/patches/
     
        
     
        
	
         Patch 1412 - IRIX 5.3 Networking Rollup Patch
	
         3MBs 8/13/96
	
         Patch 1268  - 5.3/5.3xfs combined kernel rollup patch
	
         8MBs 6/6/96
	
         Patch 1264 - XFS rollup patch for 5.3
	
         30MBs 5/1/96
	
         Patch 1102  - NFS roll up
	
         2MBs 4/3/96
	
         Patch 1095  - Scrolled Window patch
	
         2MBs 1/19/96
	
         X server roll up Choose at most one of the following
	
        
	
         Patch 1187 - excluding Impact graphics (for non-Impact systems)
	
         14MBs 3/22/96
	
         Patch 1271  - only for Impact graphics (for Impact systems)
	
         2MBs 5/1/96
	
        
	
        
   
        
        For those people with support contracts these patches are available in
        the Support Folio quarterly release CDs, and also inside Silicon Surf's SurfZone (to register, go to http://www.sgi.com/Misc/zone.html), in Supportfolio Online's 
        "Silicon 
        Graphics's support patches on the web" entry page.
       
      
      
        
              
      
        
      
        

      
      3. Possible Inst Warning Messages and Conflicts:
      
        
      There are two different types of warning messages you might see
      which are benign.  When you run the inst command "keep Same" as
      part of the prerequisite install sequence,
      you might see the warning message "No matches were found."  You can
      safely ignore it.
      
        
      After running the inst command "go," you might
      see some conflicts concerning subsystems not presently
      installed on your system.  These should offer a single
      resolution to the conflict.  The choice will be to not
      install a particular patch subsystem.  It is quite safe to
      select this single choice resolution to the conflict.
      
        
      Rhere is one error condition which might occur which will require
      some work on your part.  In a shell window, run the command "versions
      tooltalk_eoe".  If you see the subsystems
      "tooltalk_eoe.sw.links" and "tooltalk_eoe.sw.runtime" listed,
      there is nothing more to do.  Otherwise, before performing the
      prerequisite install sequence, you must locate your "IRIX 5.3" CD
      and install the two tooltalk_eoe subsytems mentioned above.  If
      for some reason you are unable to install these subsytems, then
      you will be unable to view the only two movies which are present
      on the Developer Toolbox v6.1 CD.
      
      
        
              
      
        
      
        

      
      4. A PostScript Viewing Issue:
      
        
      You will have nothing more to do, if you have already
      installed the 5.3 subsystem,
      dps_eoe.sw.dps, which provides the Netscape viewer application
      xpsview.  Without this subsystem you will not be able to view
      PostScript files on the Developer Toolbox.  Of course, you can
      arrange to use a different viewing program via your personal
      $HOME/.mailcap file and an appropriate substitute helper
      program.
      
        
      It is worth mentioning that if you do not have your own
      $HOME/.mailcap and/or $HOME/.mime.types files,
      versions of these will be created for you.  $HOME/.mime.types
      is used to augment the global default definitions
      (/usr/local/lib/netscape/mime.types) of the file
      extensions which correspond to a particular mime type.
      $HOME/.mailcap
      is used to augment the global default definitions
      (/usr/local/lib/netscape/mailcap) of the mime types
      which correspond to a particular helper application.
      There will be some Toolbox-specific
      definitions added to both of these files to help support the viewing
      of Developer Toolbox content.
      
      
      
    

      
      
    
      
    
          
      3) how to do the viewing
      
    
      
    
      
    
      
      
    
      
    
          
      4) essential information about the viewing process
      
    
      
    
      
    
      
      
    
          
      
    

      5) files placed on your workstation while running viewDT
      
    
      

    

    

    

    

end of viewDT helpfile (/CDROM/bin/helpfile)


    

    


    
    

    

    

    

start of dtCDmgr helpfile


    

    

    


    How to use the Developer Toolbox 

    
Distributed CDROM Resource Manager

    



    
    

    


    To EJECT Your Currently Loaded CD:
    

      
    
    1. press LEFTMOUSE on the CD listed in the body of the 
               dtCDmgr window (to select it)
    
    2. press the "Eject" button (second from left at bottom of window)
    
      
     NOTE:  If the eject fails you will have to do the following:
           
        
           
      • In a shell window, become super user ("su -")
           
      • Run the command "umount -k <device>", where <device>
               is the drive you want to eject  (e.g. execute 
               "umount -k /CDROM" to free up the CDROM drive device).
               Be aware: this will kill any processes using this device. 
               As long as this is only the DT, you'll be OK.
           
      • After running umount, repeat step 2 (the single-line) 
               above, and continue.
           
      
     
    3. replace the CD with the one for which you are being prompted 
     
    4. make sure the same CD device is selected (press 
                LEFTMOUSE if necessary)
     
    5. in the "Edit" pull-down menu, choose the "Refresh" menu item
     
    6. press the "Done" button (button at bottom right-corner of window). 
    
    



    
    

    dtCDmgr orientation
    


    
You probably started up this utility, dtCDmgr, by trying to go to 
an unmounted link.  This is the most typical way to start it.  You 
can also start dtCDmgr by hand in the same way you started up 
viewDT, but viewDT must already be running before you invoke
dtCDmgr.  For instance, if you started viewDT by typing 
"/CDROM/bin/viewDT", you can then start dtCDmgr after viewDT is
already running by typing "/CDROM/bin/dtCDmgr".

    
Use the dtCDmgr utility to manage local and remote CDROMs for your 
Developer Toolbox CD datasets.  For example, you can load the first 
CD in your local CDROM drive and the second and third CDs in remote 
drives.  Use the "Add..." button to add local and remote CDROM 
mount points (paths) that you use to access the other CDs and the 
information on them.  

    
NOTE:  If you only have one CDROM drive,
you must first eject your currently loaded CD and then insert the
CD for which you are being prompted.  To do this, select the CD shown in
the dtCDmgr window with LEFTMOUSE.  This will make the Eject button come alive.
Press Eject and then switch CDs.  Then using the Edit pull-down
menu, select "Refresh" to have the dtCDmgr recognize the CD you
have inserted.  The final step then is to press the "Done" button.

    
NOTE: Automount must be running in order to access remote-mounted
CDROMs.  If you are not familiar with this, see the AUTOMOUNT(1M) 
man page for more information.

    
The remote CDROM paths are specified as follows:

    

    

    
where:  

    

    
for example, /hosts/rocinante.engr/CDROM



    

    

    
    

    Important Files
    

    
$(HOME)/.www_6.1 is the temporary directory used by the viewDT command.

    
$(HOME)/.dtcdresource contains the pathnames of the local and 
remote CDROMs you configure and from which the dtCDmgr utility reads.



    

    

    
    


    User Interface
    



    


    



    
    


    Troubleshooting
    

    

If a CDROM device is busy, you cannot eject a CD.  Make sure no 
other program is using a file on the CDROM.  For instance, one 
might be editing a file of the CD, or running a program 
from the CD, etc.  Also, in any shell or dirview window, do not 
let your current working directory be any directory under 
/CDROM.  If you cannot eject a CD using the dtCDmgr utility, 
try a hardware eject (pressing the eject button on the CDROM 
drive), or use the fuser(1M) command, for example: 

    

    

    
to find out who else is using the CD.  Note the state change of 
the desktop CDROM icon, when you load or eject a CD.

    

    

end of dtCDmgr helpfile


    

    


    
    

    

    

    

    

    
janitors's corner:

    

this one is going through a particularly bad case of "notimeitis", the 
diagnosis otherwise known as the "i'm too bizi" dis-ease.  with numbness
in the right arm from too much typing, a.k.a. Repetitive Stress Injury 
(RSI), and a ruptured extensor tendon in the left hand's middle finger's 
outermost knuckle, the past months have included the beginnings of 
attempts to learn how to type differently (for the numbness) and the 
wisdom of the body stepping in to regain a missing sense of proportion 
the mind can so oft be led astray by.

    

the major efforts during the period while we endeavored to create v6.1 
was preparing and presenting our toolbox talks at the forum, updating 
swank from 5.3 to 6.2 and then getting everything we could working again 
by this august, as well as documenting what we did, strengthening and 
extending the integrity of the DT serving process, implementing as much 
of our automated-nightly-build mechanism as possible which entails 
re-imaging the internal, external, or CD image trees of the toolbox, 
re-indexing them and testing the integrity of links, and lastly 
providing support for the sgi commerce web server, https://www.sgi.com/.   where we could 
grab extra time we collected and integrated new and updated content 
for the DT.

    

we're very pleezed to have Carsten Koch's CDio Gold 
Medal software for reading and writing audio, efs and iso9660 CD 
formats.  the ReadCD and WriteCDR programs add greatly to the DT CD 
manipulation tools.  we had hoped to have a much more articulated
and explicit message at this juncture expressing our interest and desire 
to promote collaboration between ourselves and all of you of which the 
contribution Carsten has made is the most stellar current example.  we 
asked about the level of interest in this in the "Your Introduction 
to the Toolbox" labs at the forum and were pleased with the enthusiastic
responses.  the example of gdiff(1) was mentioned:  to
provide the source on the DT -- since it no longer has an owner in
engineering and is in fact no longer included on IRIX 6.2 (now replaced
with xdiff) -- so anyone could take and enhance it with the numerous 
extensions and enhancements it could adopt, then send the changes
back to us to incorporate into the DT and make this available to everyone 
else;  repeat, repeat, repeat, ...  obviously this can become a very 
powerful way to extend what we as the janitors can provide on the 
DT.  (unfortunately, it is with great regret that, due to historical 
constraints, we cannot include gdiff's source on the DT.)  yet one 
more thing we wanted to do but haven't been able to make the time 
for.  see our 18 month out 
revised-since-the-forum TODO-wish-list schedule to get a better sense 
of all we would like to accomplish.

    

it's never felt as "backed-up" as this.  a dear friend, who created 
the incredibly unique "i on Visual Computing" (http://www.sgi.com/ion/ -- see
the excellent Mouse Mauls Man!, fall'95, vol #3, ion article on RSI with 
links 
to online informational resources) was talking 
about the pace of things:  "but you've been doing this for over 10 
years -- you're used to it -- i've only been in this industry 
for a year and a half and it's unreal."  to 
which i replied, "but it's only been this way since the web kicked
in.  never has there been as much to do to keep things going, to keep
things `current'".  the urge within to do the very best possible while at
the same time not becoming thrall to the machine at the expense of 
living has never been more challenging.  this one's own web haus at
http://www.ratical.com/ has been
"on ice" since mid june.  leaving that ground fallow has been very
disheartening.  our culture's worship of the intellect, the past 
participle of intelligence, and living life placing the greatest emphasis 
on thought, the response of memory -- of everything we've ever 
experienced prior to this moment -- storing up these memories and calling
that knowledge, has imprisoned us in an idolization of the rational at the 
expense of instinctual and intuitive awareness and wisdom.  we have 
lost a fertile area of our psychic inheritance and seem determined 
to leave it lost.  present and accounted for as a birthright at the 
moment we first breathe, this irreplaceably precious universe of 
understanding and connection is shamefully neglected by the 
preeminence given to thought.  the urgent feeling for life within 
grapples with this conundrum.  for those who feel any sense of 
affinity with this, i can't recommend strongly enough a story in two 
books that has deeply touched something within more than anything 
equivalent in over 20 years:  A Story Like The Wind and A Far 
Off Place by Laurens van der Post.

    


    He did what he did instinctively.  Yet responsibility for an accurate
  report on his life forces one to ask oneself something about the nature of 
  this instinct.  One wonders whether it was not the process of growth, 
  produced by the urgent feeling for life within himself, hastening to the 
  rescue of an inexperienced and vulnerable nature, in danger of having its 
  evolution arrested, compelling him to concentrate on the growth of things in
  the world without so that their example would set in motion again growth 
  within himself.  World without and world within, after all, whether one 
  knows it or not are expressions of one another;  interdependent and 
  ceaselessly in communication, serving something greater than the sum of 
  themselves.  They are, however stern and exacting, allies of a questing 
  spirit, particularly a young spirit, charged to join them both in a little 
  garden allotment of space and time.  Happy for Francois, therefore, despite 
  the miseries of the moment, that he was free of the mistrust of instinct and
  intuition wherein contemporary Europe tends to imprison human imagination, 
  and that the pagan influences of his environment encouraged an unquestioning
  acceptance of this impulse which came to him.

    

             A Story Like The Wind, p. 123-4
    

    

    

    

    

    

    

    

    
This toolbox CD cycle has been one of maintenance, for each of us
personally, as well as with the project as a whole. Creating the DT 6.0 CD
set pushed it and us to the edge of what is possible. In fact, we/SGI are in 
the process of patenting the multi-CD website mechanism developed for the
DT v6.0. I've spent a lot of my time making the the mechanism more robust 
and to some extent helping dave with the port of the DT to IRIX 6.2. I've also
tried to do some mental/physical healing. (Those who know me will 
undoubtably mention mental improvement is not very probable.)

    
There are many, many improvements we want to effect to make the website
better.
It just seems we never have the time in which to accomplish all we'd like.
I/we are still trying to find the balance among performing miracles at
work, having a life and keeping a life. I've cut back from 14-16 hour days
to just 10-12 hour days and will have been in three musicals (after a 
ten year break) in a 3 1/2 month period ending mid September. 
It has been a rejuvinating, although tiring, path.

    
The divider art we chose is one of sustainable cultivation. It is a 
reminder of both the fundamental nature of the DT v6.1, as well
as a current goal to weave into the fabric of our lives.


    

    

    


    
    

    



Credits




    

    

    

 THIS TOOLBOX WOOD NOT HAVE BEEN POSSIBLE WITHOUT Tom Murphy's 
 continuous creation of more mechanism to generate and serve the Toolbox 
 evermore efficaciously, Rob "barefoot gaud" Toy's steadfast support in 
 updating swank to IRIX 6.2 as well as keeping it going through all sorts of 
 "system vagaries", Marc Romankewicz's unconditional support in helping to
 burn the series of trial as well as final CD WORM masters, Sophie Lonsky, 
 and Amy Gregg's indefatigable focused direction and talents to manifest 
 production of this CD;

    
 EXTRA SPECIAL THANX ALSO GOES TO 
 Donna Yobs,
 Carsten Koch,
 Chris Pirazzi,
 Michael Portuesi,
 Nelson Bolyard,
 Grant Dorman,
 Michele Chambers-Turner,
 Greg Poist,
 Micheal Minakami,
 Allen Akin,
 Kimi Bishop,
 Patrick Bouchaud,
 Ariel Faigon,
 Robert Tray,
 Kent Sandvik,
 Keith Cok,
 Dave Bouvier
 Kris Solem,
 Dave Olson,
 Todd Kulick, 
 Dave Frederick,
 Greg Ferguson,
 Robert Skinner,
 Anatole Gordon,
 Rick McLeod,
 Dave McAllister,
 Michael Stebbins,
 Ravi Shankar,
 Jim Truher, 
 Jeff McDonald,
 Caroline Lowry,
 Pete Sullivan,
 John Schimpf,
 Jessica Hardwick,
 Calvin Chinn,
 Grant Gouldon,
 Ben Mahjoor,
 Victor Riley,
 Lance Welsh, 
 Sam Leffler,
 Tom Benoist,
 Mike Gold,
 David Marsland,
 Mark Kilgard,
 Gretchen Helms, 
 Arsenio Briones,
 Bill Henderson, 
 Shabbir Latif,
 Matt Johnson,
 Judy Xavier,
 Beejay Murphy,
 Kathy Roy,
 Scott Henry, 
 Susan Lewis,
 Peter Hecke,
 Joe Ushana, 
 Boe Gatiss,
 Bob Miller,
 Andy Cameron, 
 Mike Sweet,
 Roger Chickering,
 Kathy Simpson,
 Jim Helman,
 Doug Young,
 Rod Armer,
 Callum Eastwood,
 Rhonda Rowland,
 Scott Takaoka, 
 Ken Kershner,
 Bob Green,
 Art Gary, 
 Phil Culver, 
 Ken Trant, 
 Louis Crumpler, 
 Matt Williams,
 Aaron Schuman, 
 Roger Brown, 
 David Watson, 
 Terry Drasny, 
 Ann LaGrone, 
 and
 Eva Manolis

    




    

    

    
And finally a few legal attributions:

    
Copyright © 1996, Silicon Graphics, Inc. All rights 
reserved. Specifications subject to change without notice.  Silicon 
Graphics, IRIS, OpenGL, and the Silicon Graphics logo are registered 
trademarks and Indigo Magic, Reality Engine, XFS, Indigo² Video, 
Galileo Video, IRIS GL, GL, Cosmo Compress, Sirius Video, Indy,
REACT, Indy Cam, Indy Video, IRIS InSight, IRIX, Open Inventor, 
and Silicon Studio are trademarks, of Silicon Graphics, Inc.  MIPS
is a registered trademark of MIPS Technologies, Inc.

    
FORTRAN is a registered trademark of Information Processing Technologies
Corporation.  FrameMaker is a registered trademark of Frame Technology
Corporation.  MIDI City is a registered trademark of Blue Ribbon 
Soundworks, Ltd.  PostScript is a registered trademark of Adobe Systems, 
Inc.  Motif is a trademark of Open Software Foundation.  Netscape is a
trademark of Netscape Communications Corporation.